Add sdk.paths and sdk.errorMessage to global.json #11074
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change mirrors aspnetcore PR 62619 by adding two new properties to the
sdksection ofglobal.json:paths:[ ".dotnet", "$host$" ]- Instructs the .NET CLI to probe the repository-local.dotnetdirectory before falling back to host locations, enabling automatic use of the pinned local SDK without requiring manualPATHmodifications.errorMessage: Provides clear guidance to developers when the SDK is missing, directing them to run the appropriate restore script (./restore.shfor Linux/macOS or./restore.cmdfor Windows).Benefits
PATHorDOTNET_ROOTto use the pinned SDK version..dotnetdirectory.Changes
The modification is minimal and surgical - only two properties were added to the existing
sdksection:"sdk": { "version": "10.0.100-preview.5.25277.114", "rollForward": "major", - "allowPrerelease": true + "allowPrerelease": true, + "paths": [ ".dotnet", "$host$" ], + "errorMessage": "The .NET SDK could not be found. Run ./restore.sh (Linux/macOS) or ./restore.cmd (Windows) to install the local SDK." },All other sections (
tools,runtimes,msbuild-sdks) remain completely unchanged, and the existing SDK version and configuration are preserved.Verification
.dotnetdirectory is correctly prioritized for SDK resolution💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.